[{"name":"Complianz – GDPR/CCPA Cookie Consent","slug":"complianz-gdpr","version":"7.1.0","author":"Really Simple Plugins","author_profile":"https://profiles.wordpress.org/rogierlankhorst/","requires":"5.9","tested":"6.5.5","requires_php":"7.4","requires_plugins":[],"rating":96,"ratings":{"1":36,"2":11,"3":10,"4":33,"5":1296},"num_ratings":1386,"support_threads":94,"support_threads_resolved":75,"downloaded":17066163,"last_updated":"2024-05-29 9:45am GMT","added":"2018-06-26","homepage":"https://www.wordpress.org/plugins/complianz-gdpr","sections":{"description":"

Complianz is a GDPR/CCPA Cookie Consent plugin that supports GDPR, ePrivacy, DSGVO, TTDSG, LGPD, POPIA, APA, RGPD, CCPA/CPRA and PIPEDA with a conditional Cookie Notice and customized Cookie Policy based on the results of the built-in Cookie Scan.

Features

Cookie Consent Notice

Configure a Cookie Notice for your specific region: European Union, United Kingdom, United States, Australia, South Africa, Brazil or Canada. Or use one Cookie Notice worldwide.
Configure specific cookie consent per subregion, for example: European Union + TTDSG/DSGVO/CNIL or USA + specific states for CCPA/CPRA/CTDPA etc
Cookie Consent and Conditional Cookie Notice with Custom CSS and Customizable Templates. WCAG Level AA and ADA Compliant.
Banner Templates include: GDPR-friendly Cookie Wall – Accept/Dismiss – Consent per Category – Consent per Service
Banner Templates also include; Dismiss on scroll, time on page or both based on legislation
Cookie Banners and Legal Documents conform to WCAG 2.1 AA Accessibility Guidelines and ADA Compliance.
No jQuery Dependency

Consent Management

Automatically configures you website based on wizard questions, WordPress scans and dedicated service and plugin integrations.
Blocks 3rd party cookies like Google Maps, Facebook, Instagram, AdSense, Hubspot, Recaptcha, Twitter, ActiveCampaign, and many more.
Custom integrations for plugins, themes and services are automatically detected.
Blocks iFrames, like YouTube, Vimeo, Dailymotion embedded videos and Social iFrames e.g. Instagram, Facebook et al.
Shows placeholders for blocked iFrames. Stills from videos and individual placeholders per (social) service.
Script Center to control scripts, iFrames and plugins per category or service. With dependency functionality and placeholders.
Proof of Consent: User consent registration that respects the GDPR data minimization guideline.
Periodical Cookie Scan for changes in Cookies, Plugins and 3rd Party services.
Automatically detects if you need a Cookie Notice (also called a Cookie Banner or Pop-Up).
Automatically anonymizes personal data for integrated statistics tools if needed.

Privacy Laws & Guidelines

Ready for GDPR, ePrivacy AVG, RGPD, LGPD, DSGVO, CNIL, PECR, UK DPA, UK GDPR, CCPA, COPPA, PIPEDA, CASL, POPIA, Privacy Act 1988, Australian Privacy Principles, The “Marco Civil” and the Brazilian General Data Protection Law.
Differentiate between GDPR, ePrivacy and DSGVO/CNIL or between CCPA/DNSMPI and NRS 603A, if needed.
We closely follow the latest developments in the ePrivacy regulation, the proposed Cookie Law for the European Union, and other legislation world-wide.

Legal Documents

A Cookie Policy; Generated by you with an easy wizard, drafted by an IT Law Firm.
Do Not Sell My Personal Information: DNSMPI Page for CCPA/CPRA – if required. (Now called Opt-out Preferences.)
Terms and Conditions are available in a separate plugin: Complianz – Terms and Conditions

Integrations

Detected Cookie Data is prefilled from cookiedatabase.org, with clear and transparent cookie descriptions, which are continuously updated.
Integrated with WordPress Privacy features. Export and erase personal data from our dashboard.
Implementation of Google Tag Manager, Google Analytics, Matomo, Matomo Tag Manager, Clicky, Yandex, Jetpack and Burst Statistics
Categorize your Cookies with Tag Manager or our Script Center, if needed.
\n
Integration with the WP Consent API
\n
\n
Integrates seamlessly with Gutenberg, Elementor, Divi, Forminator, WPBakery, Monsterinsights, GADWP, Beehive, WPForms, Gravity Forms, HappyForms, Contact Form 7 <5.4 (CF7), Woocommerce, Easy Digital Downloads, WP Google Maps, Google Maps Widget, Local Google Fonts, CAOS | Host Google Analytics Locally and other popular plugins.
\n
Tested with popular themes en page builders.
Gutenberg Blocks enabled.
\n
Support
\n
Complianz offers full support on the WordPress.org Forum. Before starting a new thread, please check available documentation and other support threads. Leave a clear and concise description of your issue, and we will respond as soon as possible.

Useful Links

Premium Features

Complianz offers a Full Privacy Suite for WordPress on Complianz.io with even more features:

Cookie Consent Notice

Improve conversion with A/B Testing: which cookie banner has the best consent ratio? Run tests and measure what works best for your site.

Consent Management

Records of Consent: Keep record of your consent management changes and user’s consent registration. Integrates with Proof of Consent
Respects the Do Not Track settings and Global Privacy Controls in end-users browsers.
Geo IP Cookie Consent: Cookie Consent is different everywhere. Show the correct Cookie Notice based on IP location, but only if a banner is needed.
Google Consent Mode – Use Consent Mode by Google with Google Tag Manager or Google Analytics. No further set-up needed.
Integration with TCF v2.0. An IAB Europe Consent Framework for Publishers. Registered CMP ID: 332
Data Request Forms and Registration

Privacy Laws & Guidelines

Simultaneously select USA, Canada, United Kingdom, Australie, South Africa, Brazil and the EU as targeted regions with conditional Consent and dedicated Cookie Banners.

Support for GDPR / ePrivacy – European Union with Extension for Switzerland.
Support for USA / CCPA/CPRA/CPA/CTDPA/NRS 603A/UCPA/CDPA
Support for UK-GDPR / PECR and ICO Guidelines – United Kingdom.
Support for PIPEDA and CASL – Canada.
Support for Privacy Act 1988 & Australian Privacy Principles
Support for POPIA, the South African Protection of Personal Information Act
Supports The “Marco Civil” and the Brazilian General Data Protection Law (LGPD)

Legal Documents

Privacy statements (EU, CA, UK, AU, ZA, BR & USA).
Cookie policy (EU, UK, CA, AU, ZA, BR & USA).
Impressum (Germany & Austria) & Imprint for world wide use.
Disclaimer
Terms & Conditions Integration
Processing agreements (EU, UK, CA, AU, ZA, BR & USA).
Dataleak reporting tools (EU, UK, CA, AU, ZA, BR & USA).
Supports CCPA Consent and Legal documents.
COPPA ready with Children’s Privacy Policy (USA)
Children’s Privacy Policy (UK,CA & AU)

Support & Updates

Premium Support from our amazing team.
Premium updates, new languages, features, regions and more to create the Ultimate Privacy Suite for WordPress.

About Complianz

Check out other plugins developed by Really Simple Plugins as well: Really Simple SSL

Complianz is on GitHub as well!

IMPORTANT! Complianz | GDPR/CCPA Cookie Consent can help you meet compliance requirements, but the user must ensure that all requirements are met.

Complianz provides your Cookie Policy with comprehensive cookie descriptions, supplied by cookiedatabase.org, operated by Complianz B.V. The plugin sends the results of the (local) site scan to Cookiedatabase.org, for the sole purpose of providing you with accurate descriptions and keeping them up-to-date on a regular basis. We collect for research purposes:

Cookie names
Domain that provides the cookie names
Plugin list on the domain

For more information:

Privacy Statement – Privacy Statement – Cookiedatabase.org
Terms and Conditions Database – Terms of Use – Cookiedatabase.org
Terms of Use API – Terms of Use – API – Cookiedatabase.org

Contact us if you have any questions, issues, or suggestions. Complianz | GDPR/CCPA Cookie Consent is developed by Complianz B.V.. Leave your feature requests here.

\n","installation":"

Go to “Plugins” in your WordPress Dashboard, and click “Add new”.
Click “Upload”, and select the downloaded zip file.
Activate your new plugin.
Use our tour to get familar with Complianz.

\n","faq":"\n

\nKnowledgebase\n\n

Complianz maintains a continuously growing knowledgebase about GDPR, including subregions e.g. DSGVO and CNIL, CCPA, PIPEDA, COPPA, POPIA & other specific laws on complianz.io

\nWhen do I need a Cookie Notice?\n\n

Complianz | GDPR/CCPA Cookie Consent will determine this automatically based on the laws of the region or regions, where most of your visitors come from.
\nRegarding CCPA/CPRA, you always have to show which cookies you are using but there’s no obligation in asking consent.

\nDo I always need a consent checkbox on contact forms?\n\n

Not always. The Complianz Privacy Suite Premium plugin can determine if you need this, based on your answers in the wizard. It mainly depends on the type of information and the reason why your visitor use the contact form.

\nWhat is the GDPR?\n\n

The GDPR is a regulation within the EU law on privacy and data protection for any citizen within the EU and European Economic Area. It aims primarily on giving control to individuals over their personal data. The GDPR also addresses the export of personal data outside the EU.

\nWhat is the CCPA?\n\n

The CCPA (Californian Privacy Act) is a law set up by the Californian government. The law is adjudged to be one of the toughest and farthest-reaching consumer privacy laws in the US. It is mostly focused on giving insights on what personal data business gather and how to protect and control these personal data.

\nWhat is COPPA?\n\n

The Children’s Online Privacy Protection Act (COPPA) is a law designed to protect the online privacy of children under 13. It was set up in the 1990’s and states that website owners have to meet certain requirements regarding visitors with the age under 13.

\nWhat are the Privacy Act 1988 & Australian Privacy Principles\n\n

To comply with the Australian privacy laws a website operator should present a cookie policy and/or a privacy notice before or, if that is not practicable, as soon as practicable after, your website collects personal information about an individual.

\nWhat are PIPEDA & CASL?\n\n

Canada’s Anti-Spam Legislation (CASL) and Personal Information Protection and Electronic Documents Act (PIPEDA) require a website operator to obtain consent, either implied or express consent with a dedicated cookie statement.

\nWhat POPIA (POPI Act)?\n\n

POPIA is the acronym for the South African PROTECTION OF PERSONAL INFORMATION ACT. Similar to the GDPR, the UK-GDPR, and the Brasilian LGPD, it promotes the protection of personal information processed by public and private bodies, regulates the cross-border flow of personal information, and outlines the rights of data subjects.

\nWhat are “Marco Civil” and the Brazilian General Data Protection Law (LGPD)?\n\n

The Brazilian General Data Protection Law is similar to the GDPR, the UK-GDPR it promotes the protection of personal information processed by public and private bodies, regulates the cross-border flow of personal information, and outlines the rights of data subjects. The Marco Civil is the Brazilian name of the Brazilian Civil Rights Framework for the Internet a counterpart to European’s “ePrivacy”, although not similar.

\nCan I create a Cookie Wall with this plugin?\n\n

With some custom CSS this is possible, but we do not consider a cookie wall to be GDPR compliant, so it’s not actively supported. We do, however, have the option to create a Soft Cookie Wall. Which blocks interaction with the website, but dismissing remains a possibility.

\n\n","changelog":"

7.1.0

May 14th, 2024
Improvement: Updated Google Site Kit integration
Improvement: Detection of pages with shortcode query improved for sites with a lot of pages
Improvement: limit above query to pages only, props @georgestephanis
Fix: get_required_pages not existing for documents rest_api endpoint, causing a fatal error
Fix: Data is shared with this service not saving in cookies overview

7.0.5

April 29th, 2024
Fix: compatibility with Meta Slider plugin
Fix: unexpected behaviour when editing a new, unsaved script block in the script center
Fix: Detection of Really Simple SSL pro in other plugins section
Fix: don’t replace style src with #, as this reloads the entire page as style src, props @smerriman
Fix: prefill administrator email in onboarding email
Fix: undefined array key placeholderContent in Block Editor block

7.0.4

March 9th, 2024
Fix: Purposes were incorrectly set to ‘disabled’, while there should only be a condition limiting it to the US region only, props @cdhodgdon
Fix: Pixelyoursite + pinterest function name incorrect, props @theogk

7.0.3

March 5th, 2024
Improvement: clean up MPDF temp directory after pdf generation
Improvement: set aria label on x close button from banner
Fix: deleting cookies with disallowed cookie names causing fatal error, props @baffled
Fix: missing cmplz_deny_all() function for expired cookies with a changed cookie policy id.
Fix: cmplz_set_category_as_body_class() also iterating over objects instead of just class names, when parsing the body classes, props @tomnoir
Fix: due to changed setting usage, Complianz assumed TCF active in some situations, causing the banner editor not to function properly, props @vania2008, @jeanfrancois7

7.0.2

February 28th, 2024
Fix: force the ‘wizard_completed_once’ to be true for upgrades to 7.0.2, to prevent issues with banner not showing after upgrade, props @cometto, @riroweb2022, @katynen, @julianulmer, @iviadvagency

7.0.1

February 27th, 2024
Fix: catch COMPLIANZ class not loaded yet in cmplz_get_option, props @sizilianischekueche, @franktomas, @martinellimarco, @boinich

7.0.0

February 27th, 2024
New: Rework codebase to React Framework
New: Hybrid cookie scan
New: Menu-item ‘Tools’
New: Set cookies on root domain
New: Search for plugins and services
New: Statistics block on dashboard
New: Onboarding
New: consent mode
New: Greenshift + YouTube integration
Improvement: INP performance optimisation
Improvement: catch not isset region
Improvement: add banner title to css class
Improvement: extend YoTuWP blocklist
Improvement: whitelist video lightbox in Beaver Builder
Improvement: allow text in Clarity ID input field
Improvement: DNSMPI feedback on form
Improvement: Dropped temp dir from MPDF generation, props @piccart
Improvement: use custom transient to lower number of database requests
Improvement: Added a filter to delete Records of Consent if older than X days
Improvement: E-mail obfuscation now uses the antispambot() function
Improvement: Consent area on a Twitter embed no longer links to Twitter
Improvement: Improvement: Added translatable aria-label
Fix: Elementor popup blocked content not unlocking on refresh
Fix: per site activation of single site plugin on multisite
Fix: include banner id in cache key for page links, to ensure different banner data is respected across banner ids.
Fix: jQuery exists check in Elementor integration

6.5.6

Improvement: prevent administrator from saving javascript in the css editor

6.5.5

October 12th, 2023
Fix: also clear localstorage & sessionstorage with cookie shredder
Fix: With only Canada in opt out mode selected, the question ‘will you self host Google Fonts’ was not visible
Improvement: setting a class on the parent div of a placeholder with height inherit resolves css issues on some themes, props @maxineblack
Fix: compatibility with WP Rocket when some iframes are lazy loaded, but not all.

6.5.4

September 20th, 2023
Improvement: upgrade MPDF version to 8.1.3
Improvement: prefix ‘request’ to prevent conflicts with weglot
Fix: bug in Divi Recaptcha integration
Fix: Block Editor dropping styles when in unsynced mode
Fix: Consent Mode moved to banner_loaded hook to ensure loading

6.5.3

08-08-2023
Improvement: Tested up-to WordPress 6.3

6.5.2

11-07-2023
Fix: catch missing $slug when another plugin drops the slug property

6.5.1

10-07-2023
Improvement: restore php 7.2 support in burst installer
Improvement: catch server configurations not supporting webp
Improvement: catch not existing file when generating webp
Improvement: catch not existing $slug property in auto updates check
Improvement: catch not existing ID in wordpress $post when checking for summary divs

6.5.0

04-07-2023
New: placeholders converted to wepb, loaded with lazyloading, props @james-feaver, @asafm7
Fix: CAOS host analytics locally integration fixed after constant was dropped
Fix: DNT caused wp_has_consent to always return false, which should not be the case if consent is given on a service specifically
Fix: no rt_ prefix on Tag Manager events
Fix: PHP 8.2 warnings of dynamically created properties
Fix: When TCF active, in some cases this could cause a cmlz_accept_all not defined error
Fix: Fatal error in Wizard when using “Falang”, props @chabass
Fix: cookies can not able to run in some cases due to missing variable declarations, props @sira1967

6.4.7

June 14th, 2023
Fix: WordPress 6.2 version moved the Privacy Policy function to a different file. Added fallback for older versions.
Fix: The fix for the Classic Editor bug which removes summary/details html elements, caused an issue when the post content is empty.
Improvement: if configuration by Complianz is set to false, the gtag id was added anyway, but empty.
Improvement: strings in UK cookie policy translatable, which shouldn’t be the case.

6.4.6

Improvement: unhide pagination on data requests page.
Improvement: Jersey and Guernsey included
Improvement: move nonce check to earlier in the process
Improvement: only show notice about duplicate statistics implementation if stats are actually used.
Improvement: Easy Liveblogs integration
Fix: Workaround for strange issue where the Classic Tiny MCE editor strips the summary/details tags from the unsynced legal documents html

6.4.5

Security: CSRF fixed
Fix: type=module support for scripts other than inline scripts
Fix: new shortcode handling for consent area not working for some plugin shortcodes, split in two options: default, the old one, optionally the clientside version.

6.4.4

Fix: catch not existing post_data if post structure is not following WordPress standards
Fix: exclude bricks builder from cookie blocker
Improvement: AddToAny integration updated, props @micropat
Improvement: wording and links in Canadian Cookie Policy
Improvement: mailchimp woocommerce integration feature activation after consent
Improvement: updated classic consent area to the same new structure as the new Gutenberg consent area
Improvement: script type module support in cookie blocker
Improvement: exclude cornerstone builder from cookieblocker
Improvement: new cmplz_upload_dir and cmplz_upload_url filters, to allow overrides of the plugin folders.
Dropped: Ultimate Add ons for Elementor integration, due to incompatibility issues

6.4.3

Improvement: add exclude cookies filter
Improvement: add support for parent/child themes, props @dominiccarrington
Improvement: incorrect bold paragraphs in Privacy Statement for Children
Improvement: clear blocked scripts cache on ajax save in script center
Improvement: hubspot integration improved
fix: cmplz-consent-area shortcode reload loop because of hardcoded marketing category, props @matthiaswagner

6.4.2.1

New: branding update

6.4.2

Security update: authenticated Stored XSS issue
Fix: disable cookie banner option in wizard didn’t load the complianz.js scripts, causing placeholders not to work when activated.
Fix: After switching to unlinked status in a legal document, purpose paragraph got dropped
Fix: not all categories within services showing in cookie policy overview
Fix: isset check on get_field_type function, props @moxymore
Fix: not translatable VAT ID string
Fix: With Global Privacy Control or Do Not Track enabled, and the user accepting an embedded service, the service was blocked again after a pageload.
Improvement: allow custom directory for cookie banner css generation
Improvement: catch open basedir restriction
Improvement: catch not existing accept button during initial cookie scan (no banner active yet)
Improvement: function cmplz_has_consent() in ‘other’ region returned false when no cookies present, while it should return true in that case.
New: Buttonizer integration
New: hCatpcha for WordPress

6.4.1

Improvement: do not copy over async attribute to prevent issues re-initializing scripts in some setups
Improvement: get_cookie() function performance, props @lucastello
Improvement: add space behind contact details on policy
Improvement: add our own ‘manage_privacy’ capability, as the wordpress core manage_privacy_options is not implemented consistently with other capabilities
Improvement: catch not set array class-document.php 1820
Improvement: hide blocked iframes until they’re consented to, for better UX
Improvement: PHP 8.2 compatibility
Improvement: export datarequests on symlinked folder setups (BASE_PATH -> ABSPATH)
Fix: links to processing agreement create page broken
Fix: Divi Recaptcha support
Fix: WP Go Maps Pro update
Fix: cosmetic change: cmplz_functional should always be allow, props @jidwictut9
Fix: when editing consent in unsynced mode in Gutenberg, content went missing because of automatically wrapping with divs by gutenberg and missing key props
New: Agile Store Locator integration
New: Omnisend Connect integration

6.4.0

Fix: function name error in microsoft ads integrations, props @mustafauysal
Fix: GPC & DNT in opt out regions not respected, props @ahegyes
Improvement: conditional scroll into view on consent area shortcode, props @falkemediawy
Improvement: MPDF update, props @sviluppomania
Improvement: catch CURL errors because of local SSL issues, add to system status
Improvement: return # for not existing page id in case of generated docs by complianz, but not actually generated
Improvement: Fire load event in divi integration after consent

6.3.9

Brought version in sync with premium version
Improvement: Add classes to address details
Improvement: auto installer for Really Simple SSL multisite compatible
Improvement: add filter to allow filtering data-request email recipient ‘cmplz_datarequest_email’
Improvement: translatable URLs in polylang
New: Microsoft Ads/Microsoft Clarity integration
Fix: some scripts not executing properly because of copying data-service & data-category attributes props @sophiaknows, @hamil1
Fix: new added query added to cookie block exclude to ensure Avada live builder works, props @franck_b, @markusand

\n","screenshots":"

$\"Complianz$
Complianz Dashboard: Your privacy HUB
$\"The$
The Wizard: Generate a cookie policy and configure consent management to your specific needs.
$\"Automatic$
Automatic Cookie Scan: Weekly scan of your website to keep you up-to-date!
$\"Customize$
Customize your Cookie Banner: Including template styles and a range of styling options, WCAG conform. Custom CSS available for full control!
$\"Integrations:$
Integrations: Dedicated integrations with the most popular plugins, themes and services. Feature requests are possible!
$\"Placeholders:$
Placeholders: Still images for video placeholders and individual placeholders for social media widgets. Fully customizable as well!
$\"Legal$
Legal Documents: Dedicated legal documents per region. Generated by you through the wizard, drafted, and updated by our IT Law firm.

"},"short_description":"Configure your Cookie Banner, Cookie Consent and Cookie Policy with our Wizard and Cookie Scan.","download_link":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.1.0.zip","screenshots":{"1":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-1.jpg?rev=2881064","caption":"Complianz Dashboard: Your privacy HUB"},"2":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-2.jpg?rev=2881064","caption":"The Wizard: Generate a cookie policy and configure consent management to your specific needs."},"3":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-3.jpg?rev=2881064","caption":"Automatic Cookie Scan: Weekly scan of your website to keep you up-to-date!"},"4":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-4.jpg?rev=2881064","caption":"Customize your Cookie Banner: Including template styles and a range of styling options, WCAG conform. Custom CSS available for full control!"},"5":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-5.jpg?rev=2881064","caption":"Integrations: Dedicated integrations with the most popular plugins, themes and services. Feature requests are possible!"},"6":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-6.jpg?rev=2881182","caption":"Placeholders: Still images for video placeholders and individual placeholders for social media widgets. Fully customizable as well!"},"7":{"src":"https://ps.w.org/complianz-gdpr/assets/screenshot-7.jpg?rev=2881064","caption":"Legal Documents: Dedicated legal documents per region. Generated by you through the wizard, drafted, and updated by our IT Law firm."}},"tags":{"consent":"consent","cookie":"cookie","cookie-notice":"cookie notice","gdpr":"GDPR","privacy":"privacy"},"versions":{"6.5.6":"https://downloads.wordpress.org/plugin/complianz-gdpr.6.5.6.zip","7.0.1":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.0.1.zip","7.0.2":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.0.2.zip","7.0.3":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.0.3.zip","7.0.4":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.0.4.zip","7.0.5":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.0.5.zip","7.1.0":"https://downloads.wordpress.org/plugin/complianz-gdpr.7.1.0.zip","trunk":"https://downloads.wordpress.org/plugin/complianz-gdpr.zip"},"donate_link":"https://paypal.me/complianz","icons":{"1x":"https://ps.w.org/complianz-gdpr/assets/icon-128x128.png?rev=2881064","2x":"https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064"}},{"name":"Be POPIA Compliant","slug":"be-popia-compliant","version":"1.3.0","author":"Web-X | For Everything Web | South Africa","author_profile":"https://profiles.wordpress.org/bepopiacompliant/","requires":"5.4","tested":"6.5.5","requires_php":"7.3","requires_plugins":[],"rating":100,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":3},"num_ratings":3,"support_threads":0,"support_threads_resolved":0,"downloaded":3741,"last_updated":"2024-04-13 12:26pm GMT","added":"2021-12-09","homepage":"https://bepopiacompliant.co.za","sections":{"description":"

The only POPIA Compliance plugin that is NOT JUST a Cookie Banner!
\nUse Be POPIA Compliant and ensure your website is 100% POPIA Compliant in as little as 15 minutes with PRO.
\nWe also provide a checklist with all the conditions as per the Protection of Personal Information Act, Act 4 of 2013. If you’d rather read up by yourself, please visit https://bepopiacompliant.co.za/popia/act/index.php for the full legislation. Using our PRO Be POPIA Compliant Plugin, you will already be able to receive consent process data requests and data deletion requests automatically, without any need to intervene!

Fun Fact: There is not a single mention about cookie banners in the POPIA Act, and yet many website owners think that is all they require to be POPIA Compliant.

NOTE: INSTALLING THIS PLUGIN ALONE DOES NOT MAKE YOUR SITE POPIA COMPLIANT. COOKIES, IS REQUIRED BY GDPR, BUT NOT POPIA SINCE THERE IS MUCH MORE TO BE CONSIDERED. YOU NEED TO ENSURE YOU HAVE COMPLETED EVERY STEP IN THE POPIA CHECKLIST. YES, WE KNOW… IT IS GOING TO TAKE SOME TIME TO GET ALL OF THAT IN ORDER. AND THEN YOU STILL HAVE TO PROCESS DATA REQUESTS MANUALLY. THAT IS EXACTLY WHY WE OFFER THE PRO VERSION SO THAT YOUR SITE IS COMPLETELY POPIA COMPLIANT IN AS LITTLE AS 15 MINUTES, WITH MINIMAL TO NO FURTHER ACTION FROM YOU IN FUTURE.

3rd Party and External Services

For our plugin to work on your site, we rely on our server to communicate with your plugin. This 3rd party service together with the circumstances under which we make calls are documented herein:

We make calls to our server, using our plugin from your WordPress website. This enables us to perform data requests on your behalf, as well as to send you notifications, and to do certain checks so you get the best we have to offer. For your security we have codded the calls in such a manner, to only allow transmission between sites that contain our plugin and our server with a specific URL only. Each call is signed with your API Key and therefore no unauthorised calls can be made to our server, and no calls are ever made to the Be POPIA Plugin on your site. We add a single cronjob via our plugin to run data requests every hour.

Link to service: https://bepopiacompliant.co.za/
\nLink to service Privacy Policy: https://bepopiacompliant.co.za/#/privacy/80

Below is a list of calls we make together with a description of what is being transmitted and for what reason:

https://py.bepopiacompliant.co.za/api/newusercreated
\n– each time a user registers on your website, we collect your domain name, user ID and email address and send it to our database to log an entry so that we can collect further data that you store about that user in the case of a data request.

https://py.bepopiacompliant.co.za/api/plugindetailscheck/“server_name”
\n– we collect your domain name to check if your domain is registered with us to use our plugin.

https://py.bepopiacompliant.co.za/api/plugindetails/$id
\n– to indicate whether our plugin is active, inactive or deleted from your website.

https://py.bepopiacompliant.co.za/api/plugindetails/
\n– to indicate when our plugin is installed on your website.

https://py.bepopiacompliant.co.za/api/domain/”server_name”
\n– to get data from our database to indicate that you completed the PRO steps and save it to your database.

https://py.bepopiacompliant.co.za/api/getmessage/
\n– to show you any notifications about POPIA updates in your admin panel, that we might need to share.

https://py.bepopiacompliant.co.za/api/plugindetailscheck/“server_name”
\n– to show a message if we disapprove of the use of our plugin on your website, especially if we determine that you do not comply with POPIA using the free version, but claims that you are compliant. Misuse of our plugin may result in a suspension after which a thorough inspection will be required to determine whether your plugin should be reinstated.

These inspections shall be billed at R500 per inspection request before the inspection is initiated. If we have found after any inspection request that your plugin is still not used correctly, we will provide you with a report of all fixes that are required. After fixing those problems, you shall be required to submit a follow-up inspection request and again pay an R500 inspection fee before we do the inspection. When we are satisfied that all the requirements are met and that your site is POPIA Compliant, we shall reinstate your plugin.

Alternatively, you can sign up for the PRO version of BE POPIA Compliant in order to wave the inspection and reactivation costs.

https://py.bepopiacompliant.co.za/api/domainapicheck/$company_key
\n– to validate your entered key for using the PRO Version of Be POPIA Compliant in our database to ensure you are registered with us as a Pro Member.

https://py.bepopiacompliant.co.za/api/domain/check_expiry/”server_name”
\n– to check whether your PRO Membership is up to date and paid in full.

\n","installation":"

Install from WordPress Library

Log in to the admin panel of your WordPress website, click on “plugins”, then again at the top left on “Add New”.
\nNow type “POPIA” into the search bar and wait for the plugins to filter. Note that at the date of recording, none of the other plugins provides any bonified solution to POPIA, even though stating it. They merely provide cookie consent options that are only a small portion of the POPI Act requirements and are already included in our plugin, should you choose to use it. Now click on “Install Now” on the BE POPIA COmpliant Plugin. After installation, activate the plugin. Thereafter you will find the heading “POPIA Compliance” in the left-hand menu under “Dashboard”.

Install From Website
\nThe link on our website will take you to our official Plugin Page on WordPress.
\nAlternatively, you can go straight there by visiting: https://wordpress.org/plugins/be-popia-compliant/

Click on the download button to download the latest official zipped file of our plugin. Now log in to the admin panel of your WordPress website, click on “plugins”, then again at the top left on “Add New”. Thereafter click on “Upload Plugin” and select or drag and drop the file you just downloaded.
\nAfter installation, activate the plugin. Thereafter you will find the heading “POPIA Compliance” in the left-hand menu under “Dashboard”.

\n","faq":"

Q1: What is a cookie anyway?
\nA1: A cookie is a digital record, (text files with small pieces of data), stored on your computer, or better, in your browser. This is used to track, personalise and save information about each user’s session. Any data can be stored and retrieved from a cookie. It is up to the developer of the site or system what goes in there. Cookies let websites remember you, your website logins, shopping carts and much more information. But they can also be a treasure trove of your private information for criminals to spy on.
\nThis being said, having a Cookie notice or giving consent to having cookies stored in your browser, is but one small segment of the many regulations to be implemented to Be POPIA compliant.

Q2: What is POPIA?
\nA2: POPIA stands for the Protection of Personal Information Act, Act No. 4 of 2013 or POPI Act. This law has been with us for a while but took effect on July 1, 2020, and enforcement began on July 1, 2021. Due to technical difficulties, small business owners have got until February 1 2022 to get their act together. At this stage, it is still uncertain how strict the authorities will act on those that are not POPIA compliant. The provisions for penalties on the other hand is no mystery, and actually quite alarming!

Q3: Is there a difference between POPI and POPIA?
\nA3: Yes and no. POPI is the act or rather action of Protecting Personal information. This implies that all the policies, procedures, processes and practices in the organisation relating to personal information, are in fact doing POPI. POPIA is merely the name of the law.
\nIn summary, to comply with POPIA, you need to implement a POPI programme.

Q4: What is POPI act compliance?
\nA4: Generally, compliance means adhering to a rule, such as a policy, standard, specification, or law. This means to be POPIA compliant you need to follow all the rules and regulations as set out in the POPI Act as well as the code of conduct regarding POPIA.

Q5: Should I be Compliant?
\nA5: According to the POPI Act, if you have a filing system, on paper or digital, localised or scattered containing personal information about ten (10) or more people, you need to be compliant. It is only if you have received an express exemption from the government, that you need not comply.

Q6: I am running a small online business on the side as a sole proprietor can I be prosecuted?
\nA6: Yes, unfortunately, you are directly liable and may be fined or may end up in prison or both. We suggest you register a company to protect yourself from any unforeseen judgements. You will still be held liable, but there is a small barrier between owners of a company and the company, since the company if registered is seen as a juristic person.

Q7: What happens if we don’t comply with POPIA?
\nA7: There are significant consequences for non-compliance, including up to R10 million rands in fines or up to 10 years in prison, or both.

Q8: What is considered personal information?
\nA8: Personal information is any information about an identifiable living, natural person or a juristic person including but not limited to race, gender, sex, sexual orientation, marital status, nationality, age, physical or mental health, disability, language, education, any data relating to medical, financial or employment records, ID number, email address, physical or postal address, location info, phone numbers, blood type or biometric data, personal opinions or references, private or confidential correspondence or even views or opinions of another person about you.

Q9: What is a data subject?
\nA9: Any person, a living natural person, or a juristic person, that’s data is being processed.

Q10: What is generally considered a breach of POPIA?
\nA10: The following is the common breaches:
\n– Loss of personal information due to inadequate security safeguards
\n– Collecting personal information without having obtained the necessary consent
\n– Sending personal information to people who are not supposed to have it
\n– Breach of security safeguards (network with personal information is hacked)
\n– Not complying with an enforcement notice issued by the Information Regulator
\n– Processing special personal information without there being a necessity

Q11: I am a visitor to the site, should I be somehow compliant?
\nA11: No, the POPI Act is there for your safety. The regulations imposed by POPIA, all act as safeguards so that each user’s info gets looked after and is not recklessly being utilised in such a manner that your information may fall into the hands of unauthorised persons. Therefore, it is in your interest to insist on signing a consent form, so you can manage your consent by limiting the data being collected and disseminated.

Q12: How do I register my information officer with the regulator?
\nA12: A responsible party should register their information officer and deputy information officer if relevant on the Information Regulator Registration Portal.

Q13: Can one person be the information officer for multiple entities?
\nA13: Yes, one person can be the information officer of multiple entities. And for now, as long as the deputy information officer is also the same for the same multiple entities, you can manage all those entities from one account on the Be POPIA Compliant platform. If however there are a different data officer or deputy data officer in one of your organisations, we suggest creating a new account for those entities. As for the Information Regulator Portal, it is not currently supported to be the data officer for multiple entities.

Q14: I am running a small business by myself, do I need a deputy information officer?
\nA14: No, by default the head or CEO of an entity is deemed the data officer. If however there is too much work and it is decided that a deputy officer takes over the duties from such head, a deputy officer may be appointed. Note however that the head of the entity remains liable for the actions of the deputy information officer.

Q15: If my entity is found guilty of an offence, who will pay the fine, or go to jail?
\nA15: This is rather a complex matter since it depends on the entity type. If you are a sole proprietor, you are automatically held responsible. In the event of a partnership for instance all partners may be held liable. If a deputy information officer was appointed according to Annexure C of the guidance notes, still, the default information officer or head of entity shall be liable. So if you are the CEO or Managing Director, consider yourself warned. The aforementioned is typically the case, but if it can be proved that a certain employee, for instance, stole and sold personal information, that employee shall be punished for the offence.

Q16: Does it not make sense that the Chief Information Officer or CTO, from IT, be also appointed as the Information Officer?
\nA16: It is best not to since they are largely concerned with the technology aspect of operations. Many other people in the organisation could lead to an offence being committed. In such a case, it would mostly be unfair towards the CTO since they do not likely communicate with anyone in sales or otherwise. It is probably best to assign someone in HR or appoint a new person altogether.

Q17: Can we outsource this duty of the data officer to someone else?
\nA17: This is not recommended, since they might not have a full understanding of your entire process flow in your organisation. And since ultimately the head of the institution shall still bear the responsibility, do you want to take that chance?

Q18: I was appointed as the information officer, is there some sort of guide?
\nA18: The information regulator published a guideline that you can download.

Q19: Are there any other laws that are linked to POPIA?
\nA19: Yes, the following laws have an impact on POPIA:
\n– Consumer Protection Act, or (CPA)
\n– National Credit Act, or (NCA)
\n– Regulation of Interception of Communications Act, also known as (RICA)
\n– Promotion of Access to Information Act, or (PAIA)
\n– Electronic Communication Act
\n– Cybercrime Bill, and
\n– Your Constitutional Right to Privacy as defined in the Bill of Rights

Q20: Who can use Be POPIA Compliant?
\nA20: If you have a website, that collects any data such as customer emails, telephone numbers or addresses, you will have to comply. Any person operating a hobby or a fully-fledged business with more than ten (10) customers needs to comply. If you have a WordPress website, we currently offer an easy to use a plugin for WordPress users. We also offer integration options for custom-developed systems and Apps. If your solution is not a WordPress solution, we shall need to establish through a consultation how your current program works, and how POPIA influences your business flow. From there we will be able to provide you with a detailed report on what changes, your development team need to get into place together with the endpoints that data need to be sent to, and collected from.

\n","changelog":"

1.3.0

* Added security patch\n

1.2.0

* We made changes so that PRO Features are completely segregated from the Free Version of the plugin.\n

1.1.11

* All WooCommerce Privacy Policies is now being overwritten by BPC in PRO\n

1.1.10

* Fixed error not detecting ID Number on Checkout\n

1.1.9

* Changed Consent related calls to call from manage Consent, rather than from Be POPIA Compliant. \n

1.1.8

* Added support to PRO version for data processing via ARForms - PayFast Addon Plugin.\n* Data deletion via PRO Version can now be delayed for any predefined period as per requirements of superseding laws and regulations such as FICA and more.\n* Tested compatibility with WordPress 6.\n

1.1.7

* Fixed a bug where cookie settings tab was not displaying settings.\n

1.1.6

* Added settings (now Banner & Cookie Settings) for PRO version to customize the POPIA Compliant Banner for a more elegant look.\n* Fixed blank space at bottom of the page in some instances.\n* Fixed a vulnerability that exposed email addresses when a specific link was followed.\n

1.1.5

* Added functionality to capture ID Number and passing it over to Consent form for autofill.\n* Added functionality to only request consent on checkout, if consent has not yet been provided.\n

1.1.4

* Refactored Reports\n

1.1.3

* Fixed unclosed '(' on line 1762...\n

1.1.2

* Fixed wrong location of closing bracket.\n* Added ID Validation on WordPress Registration.\n

1.1.1

* Fixed wrong version number.\n

1.1.0

* Added the following functionality:\n*   For free plugin users: \n    *  To be able to add their user preferences to each user.\n    *  To upload consent forms and then save the generated link for each user in the user settings.\n    *  To also add the Identification Number.\n    *  Also the Type of Identification used and the Country of Issue if this is not a South African ID Number.\n*   For PRO Be POPIA Plugin users:\n    *  To display all the above details in the users' table. (This is all managed automatically by the PRO Be POPIA Compliant Plugin).\n    *  Programmatically handle Data Requests.\n    *  Authenticate users, then send data to authenticated users (with no action by you).\n    *  Programmatically handle Data Deletion Requests.\n    *  Authenticate users, then Redact all personal data for that authenticated user in your database (with no action by you).\n    *  Added basic support for WooCommerce - to request consent when registering, or on checkout.\n

1.0.17

* Fixed - Free banner disappears when registering on BPC Website without company info.\n

1.0.16

* Fixed Calculation proplem on Checklist.\n

1.0.15

* Added Hidden Version number for easier debugging.\n

1.0.14

* Fixed file not found in some instances\n

1.0.13

* Tested compatibility for WordPress 5.9.\n* Added Links to Main Plugin Menu for ease of navigation.\n

1.0.12

* Fix - Error in pinging API.\n* Fix - Can’t activate plugin: Fatal Error\n* Fix - Simplified API Call to improve performance\n

1.0.1

* Added functionality on PRO for emails to be sent for collecting consent once a user registers on your site (Ensure you ask for email as usernames)\n

1.0.0

* Initial Be POPIA Compliant Plugin\n

\n","screenshots":"

$\"Be$
Be POPIA Compliant (BPC) | Dashboard - This gives you a brief overview of the BPC plugin.
$\"Be$
Be POPIA Compliant (BPC) | Checklist - Complete all these instructions and tick them as you complete them.
$\"Be$
Be POPIA Compliant (BPC) | Cookie Settings - Customize your Cookie Notice Banner to match your brand.
$\"\"$
$\"\"$

"},"short_description":"The only POPIA Compliance plugin that is NOT JUST a Cookie Banner! For any site that operates in South Africa. *Get your site compliant in as little a …","download_link":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.3.0.zip","screenshots":{"1":{"src":"https://ps.w.org/be-popia-compliant/assets/screenshot-1.png?rev=2942351","caption":"Be POPIA Compliant (BPC) | Dashboard - This gives you a brief overview of the BPC plugin."},"2":{"src":"https://ps.w.org/be-popia-compliant/assets/screenshot-2.png?rev=2942351","caption":"Be POPIA Compliant (BPC) | Checklist - Complete all these instructions and tick them as you complete them."},"3":{"src":"https://ps.w.org/be-popia-compliant/assets/screenshot-3.png?rev=2942351","caption":"Be POPIA Compliant (BPC) | Cookie Settings - Customize your Cookie Notice Banner to match your brand."},"4":{"src":"https://ps.w.org/be-popia-compliant/assets/screenshot-4.png?rev=2942351","caption":""},"5":{"src":"https://ps.w.org/be-popia-compliant/assets/screenshot-5.png?rev=2942351","caption":""}},"tags":{"be-popia-compliant":"Be POPIA Compliant","bepopiacompliant":"BePOPIACompliant","popi":"POPI","popi-act":"POPI Act","popia":"POPIA"},"versions":{"1.0.0":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.0.zip","1.0.12":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.12.zip","1.0.13":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.13.zip","1.0.14":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.14.zip","1.0.15":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.15.zip","1.0.16":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.16.zip","1.0.17":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.17.zip","1.0.3":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.3.zip","1.0.4":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.4.zip","1.0.5":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.5.zip","1.0.8":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.8.zip","1.0.9":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.0.9.zip","1.1.0":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.0.zip","1.1.10":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.10.zip","1.1.11":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.11.zip","1.1.2":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.2.zip","1.1.3":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.3.zip","1.1.4":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.4.zip","1.1.5":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.5.zip","1.1.6":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.6.zip","1.1.7":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.7.zip","1.1.8":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.8.zip","1.1.9":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.1.9.zip","1.2.0":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.2.0.zip","1.3.0":"https://downloads.wordpress.org/plugin/be-popia-compliant.1.3.0.zip","trunk":"https://downloads.wordpress.org/plugin/be-popia-compliant.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/be-popia-compliant/assets/icon-256x256.gif?rev=2942351","2x":"https://ps.w.org/be-popia-compliant/assets/icon-256x256.gif?rev=2942351"}},{"name":"Essert Privacy Compliance","slug":"privacy-security-compliance","version":"1.3","author":"Essert Inc.","author_profile":"https://profiles.wordpress.org/dvsub/","requires":"5.0","tested":"6.0.9","requires_php":"7.0","requires_plugins":[],"rating":0,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"downloaded":384,"last_updated":"2022-11-25 6:24pm GMT","added":"2022-08-25","homepage":"https://essert.io/essert-privacy-compliance-automation/","sections":{"description":"

Essert Privacy Compliance plugin assists businesses and web masters to comply with California Consumer Privacy Act (CCPA), CPRA, GDPR, POPI Act, Virginia CDPA, Colorado Privacy act, Utah privacy law, Connecticut privacy law, and more. It creates a privacy request intake form and Do Not Sell My Personal Information Button. This plugin in free. You could manage and automate your requests with a web application.

Major features in Essert Privacy Compliance plugin include:

Get started with a specific worklist
Get your compliance setup completed faster
Modify all your policies collaboratively with your team using our templates
Automatically create a consumer privacy intake request page for your website.
Automatically create a Do Not Sell My Personal Information Button for your website.
Assists in Rapid CCPA Compliance and Roll Out.
Provides easy workflow to manage consumer privacy requests with role-based access.
Provides agencies to help manage your consumer privacy requests.
Provides a simple consumer email address verification.
Provides the ability to customize your consumer privacy intake form.
Provides configurable email templates to respond to consumer privacy requests.
Assists in multi-user workflow to respond to privacy requests.
Delivers a detailed dashboard to track consumer privacy requests.
Assists in attaching data or documents in responses to consumer privacy requests.
SignUp on https://essert.io to manage all your privacy requests.
\n** These are some premium features
\n** Respond using your own email domain
\n** Use one-time password to further verify consumer requests
\n** Fully automated Toll Free Number for consumer requests intake
\n** Weekly reports and alerts
\n** Download privacy Requests

** PS: You’ll need an app.essert.io Secret Key to use it. Keys are free ** for all websites.
\n** SignUp page: https://app.essert.io/ or https://essert.io/sign-up-sign-in/
\n** Terms of Service :: https://essert.io/terms-of-service/
\n** Privacy policy :: https://essert.io/privacy-statement/
\n** Pricing page for premium features :: https://essert.io/pricing/
\n** Contact us or support page:: https://essert.io/contact/

Our plugin privacy policy:
\n– We do not track any of your users or visitors on your website
\n– We do not track any of your users or visitors on the web application
\n– The only information we store is your consumer privacy requests (request data) which is the service we offer
\n– We do not have access to your request data unless you explicity give us permission for the specific purpose of support
\n– We require you to provide email ID to register to the free web application connected to this plugin
\n– We do not offload any of your website assets that are unrelated to our service
\n– We do not sell any of your personal information
\n– We do monitor the admin usage of the plugin for the specific purpose of support, marketing and product enhancements

\n","installation":"

\n
Upload the Privacy Requests for CCPA Compliance plugin to your website, Activate it, then enter your [app.essert.io Secret key].
\n
\n
Use shortcodes provided by the plugin to deploy DSAR forms and Do Not Sell My Personal Informaiton Button
\n
\n
Use shortcodes provided by the plugin to deploy privacy policies, website terms of use and more
\n

1, 2, 3: You’re done!

\n","faq":"\n

\nHow does it work?\n\n

Essert software is a SaaS product. And, we provide this WordPress plugin for easy deployment.

Step 1 is to sign-up on app.essert.io, and onboard (by selecting one of the free or paid compliance worklists).

Step 2 is to sign-in from the WordPress plugin and get the secret code.

Step 3 is to publish the privacy intake forms and/or buttons using shortcodes in the request forms tab.

Step 4 is to publish all public policy notices or disclosures intake forms on your website, using shortcodes in the policies tab.

Step 5 is to test one of the forms to ensure that you receive the requests on the app.essert.io

\nOur website is managed by an external agency, what should they do?\n\n

You have two options. Option 1 is to add your agency as a partner user. Option 2 is to email the two (2) forms to them and give them instructions to deploy the forms on your website. You or your agency may customize the forms as you see fit.

\nAre the intake forms customizable?\n\n

Yes. You may customize the intake forms. On app.essert.io, we provide HTML files for privacy intake. Anyone of your team members or your agency team with knowledge of HTML can easily customize these intake forms.

\nDo you provide privacy policy templates for use?\n\n

Yes. While we do not provide any legal advice, we provide a privacy policy template, and several other policy templates including website terms of use, social media policy and more. Our privacy policy template was authored by a privacy attorney and is provided to you as is. We do recommend that you consult an attorney, or call us to get our suggestions for changes. You may publish this privacy policy template using shortcodes. You may edit and customize the privacy policy template using app.essert.io and maintain a auditable record of any changes.

\nHow much does Essert cost?\n\n

Essert has both free and paid offerings. All the features that you need to get started for privacy compliance are included at no cost to you in our free worklist. There are no limits on the number of users, number of requests, or number of email templates you need to process consumer requests. For more information on pricing visit https://essert.io/pricing.

\nWhat are the premium features of the Essert product?\n\n

One of the premium features of Essert is an the Advanced California Privacy Compliance worklist. For more information on pricing visit https://essert.io.

\nHow to deploy the shortcodes that are provided in the plugin?\n\n

If you are the website administrator, please follow these simple steps:

Step 1: Add a new page
\nStep 2: Paste the shortcode as-is in the new page content
\nStep 3: Name the page appropriate and publish it
\nStep 4: Link the published page in other areas of your website

If your website is managed by an external web admin, we believe they would have a team who could repeat the steps above

\n\n","changelog":"

1.0

*Release Date – July 12, 2022

\n"},"short_description":"Essert Privacy Compliance plugin assists businesses and web masters to comply with California Consumer Privacy Act (CCPA), CPRA, GDPR, POPI Act, Virgi …","download_link":"https://downloads.wordpress.org/plugin/privacy-security-compliance.zip","screenshots":[],"tags":{"california-consumer-privacy-act":"California consumer privacy act","ccpa":"CCPA","ccpa-compliance":"CCPA compliance","cpra":"CPRA","privacy-compliance":"Privacy compliance"},"versions":[],"donate_link":"","icons":{"1x":"https://ps.w.org/privacy-security-compliance/assets/icon-128x128.png?rev=2776092","2x":"https://ps.w.org/privacy-security-compliance/assets/icon-256x256.png?rev=2776092"}}]

POPI Act

Complianz – GDPR/CCPA Cookie Consent

Be POPIA Compliant

Essert Privacy Compliance

Get New Themes & Resources